-
Notifications
You must be signed in to change notification settings - Fork 552
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: rust coverage test meets compile error for missing debuginfo #1740
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #1740 +/- ##
==========================================
+ Coverage 28.87% 29.12% +0.25%
==========================================
Files 49 49
Lines 17202 17468 +266
Branches 8268 8470 +202
==========================================
+ Hits 4967 5088 +121
- Misses 7221 7297 +76
- Partials 5014 5083 +69
... and 21 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
I would like to see a test for that please. Thanks |
I don't know how |
I found the feature was introduced cuz Lines 536 to 542 in 4a8b5f5
in the same PR, the author try to keep Lines 550 to 556 in 4a8b5f5
tbh I have no idea how sccache deal with those |
yeah. I think I found that when we try to do coverage test, in but in btw, I tested it in this repo https://github.com/yihau/sccache-coverage-build-error |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
copied the mechanism from c complier
Mostly LGTM! Can you add a job which uses rust coverage to make sure it works? I think we can add a new job called |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly LGTM, thanks a lot!
hi, thanks for quick review! I'm from the same org (@solana-labs) with @yihau
i couldn't decipher the error from the ci build...
so, it looks like the regression window is quite narrow: rust-lang/rust@bd39bbb...ef934d9 among them, this came to my attention: rust-lang/rust@6f38fd5, rust-lang/rust#107778 which in turn contains this: rust-lang/cargo#11252 |
I believe this CI failure is not related to this PR. Please ignore it. |
@@ -609,3 +609,32 @@ jobs: | |||
${SCCACHE_PATH} --show-stats | |||
|
|||
${SCCACHE_PATH} --show-stats | grep -e "Cache hits\s*[1-9]" | |||
|
|||
issues-1652: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please rename the test for something more explicit?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you have any prefer name? is missing-debug-info
a good name?
strategy: | ||
fail-fast: false | ||
matrix: | ||
version: [nightly-2023-02-08, nightly-2023-02-09] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it necessary to hard-coded the date?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found it's broken since the version nightly-2023-02-09
so I choose those two version to test.
I would prefer that you extend it to test coverage in general
Le ven. 21 avr. 2023, 07:53, Yihau Chen ***@***.***> a écrit :
… ***@***.**** commented on this pull request.
------------------------------
In .github/workflows/integration-tests.yml
<#1740 (comment)>:
> @@ -609,3 +609,32 @@ jobs:
${SCCACHE_PATH} --show-stats
${SCCACHE_PATH} --show-stats | grep -e "Cache hits\s*[1-9]"
+
+ issues-1652:
do you have any prefer name? is missing-debug-info a good name?
—
Reply to this email directly, view it on GitHub
<#1740 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFTBDSMVDR5X6RWXYTWSXDXCIOG5ANCNFSM6AAAAAAXE7DNKE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
oh. do you mean that 1) change job name to |
Hi @sylvestre, I have a diff in my local. it looks like: diff --git a/.github/workflows/integration-tests.yml b/.github/workflows/integration-tests.yml
index cf3e909..3ad4cbe 100644
--- a/.github/workflows/integration-tests.yml
+++ b/.github/workflows/integration-tests.yml
@@ -610,14 +610,9 @@ jobs:
${SCCACHE_PATH} --show-stats | grep -e "Cache hits\s*[1-9]"
- issues-1652:
+ rust-test-coverage:
runs-on: ubuntu-latest
needs: build
-
- strategy:
- fail-fast: false
- matrix:
- version: [nightly-2023-02-08, nightly-2023-02-09]
steps:
- uses: actions/download-artifact@v3
with:
@@ -628,11 +623,11 @@ jobs:
- name: Coverage test
run: |
- rustup toolchain install ${{ matrix.version }}
+ rustup toolchain install nightly
cargo new hello
cd hello
echo "serde = { version = \"1.0\", features = [\"derive\"] }" >> Cargo.toml
- cargo +${{ matrix.version }} test
+ cargo +nightly test
env:
RUSTC_WRAPPER: /home/runner/.cargo/bin/sccache
CARGO_INCREMENTAL: "0" I will push this code if you think it is better |
yeah, exactly what I was expecting :) |
This PR seems ready to go now. @sylvestre Do you wanna to take another look? |
seems we didn't push to crates.io in our release workflow. |
Hi @Xuanwo, does this one look correct?
Close #1652